home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1996 #15
/
Monster Media Number 15 (Monster Media)(July 1996).ISO
/
renegade
/
rgsn0696.zip
/
RGSFDN.POL
< prev
next >
Wrap
Text File
|
1995-07-18
|
9KB
|
208 lines
R G S N E T
Renegade Support Network
IFDC Filegate Policy Document
FDN: RGSNet (The Renegade Support Network)
HeadQuarters (ZC): Scott Freeman, 1:219/801
FileBone Tech Coordinator (FC): Mike Fergione, 1:104/651
May 11, 1995
(revised 7/16/95)
=============================================================================
1.0 THE RGSNET FILE DISTRIBUTION NETWORK
The "RGSNet File Distribution Network" as it relates to the IFDC
(International File Distribution Cooperative) Filegate Project <sm>,
hereinafter called RGSFDN, consists of a system of BBS's belonging to
the RGSNet Renegade BBS oriented network. The guiding concept of the
RGSFDN is to provide a wide ranging area of Renegade and related BBS
oriented files to the RGSNet membership, and to provide a reliable
distribution service to authors wishing to distribute their programs.
1.1 FILES CONTENT
The RGSFDN and it's member boards will distribute files that fall under
the "Shareware" concept as defined by the Association Of Shareware
Professionals <ASP>. It is expressly and specifically PROHIBITED for
an RGSFDN member to distribute ANY type of commercial or pirated
software.
============================================================================
2.0 HIEARCHY AND MANAGEMENT
The management of RGSFDN activity will be accomplished by the RGSNet
Zone Coordinator (ZC) and the RGSNet Files Coordinator (FC).
2.1 ZONE COORDINATOR (ZC)
The ZC is the ultimate authority for the RGSFDN. It is the responsibility
of the ZC to appoint and monitor the performance of the FC. The ZC alone
will decide upon the appointment to, and removal from, office of the FC.
2.2 FILES COORDINATOR (FC)
The FC is responsible for the day to day management of the RGSFDN and
will provide the ZC with updates to the master copy of the RGSFDN File
Echos, as well as regulate the hatching of files into the File Echos.
The FC has responsibility for the overall guidance of the network and
it's activity. These responsibilities embrace the public aspects of
RGSFDN policy, publicity, contacts with other organizations and most
importantly, processing files for distribution. The FC will also
moderate the RGS_FILE Message Echo.
The FC will act in his/her capacity to develop and implement any changes
in this policy document as required. It is expected that the FC will
solicit the advice of the RGSNet members when forming policy changes.
============================================================================
3.0 DISTRIBUTION
Primary distribution is accomplished thru direct connection of the
FC System(s) to the assigned IFDC Filegate Hub. The ZC will act as a
direct conduit to the RGSFDC Regional Coordinators (RC) from the FC.
Regional Coordinators will connect directly to the ZC system to receive
the RGSFDN activity with exceptions made only with ZC approval.
RC's will feed RGSFDN activity to their Net systems. Net systems, in
turn, will feed the RGSFDN activity to the end user systems.
3.1 UPLOADING/HATCHING OF FILES
No one is allowed to upload or hatch files into the RGSFDN areas except
the ZC or the FC. New files to be added to the system will be sent to
the ZC or FC for hatching into the network. All RGSFDN files hatched into,
and received from the IFDC Filegate will be processed in their respective
File Echo using a "TICK" compatible file processing program.
============================================================================
4.0 SYSTEM REQUIREMENTS: ZC/FC/RC
All systems handling RGSFDN activity and interacting directly with the
IFDC Filegate Project <sm> are required to be Crash Mail configured
systems with up to date netmail and file processing capabilities,
High Speed USRobotics modems (28.8k V.34 VFC) and enough disk space
to hold a few months worth of RGSFDN files.
It is MANDATORY that any system handling RGSFDN activity have the full
complement of RGSFDN File Echos configured. Whether files are kept in
the area is at the discretion of the system operator, but the minimum
standard for these areas is that they be Pass-Thru configured for "TICK".
4.1 SYSTEM REQUIREMENTS: ALL RGSFDN SYSTEMS
RGSFDN activity consists of automated files passing among amateur and
professional netmail capable bulletin board systems using FidoNet
Technical Standards of Communications. Requirements for RGSFDN activity
are:
Receive your RGSFDN activity from an approved RGSNet system.
Permanently post for download the RGSNet information file
containing the RGSNet Policy Document(s) and, update the file
when a revised version is received.
============================================================================
5.0 POLLING
RGSFDN SysOps are not allowed to charge a fee to other RGSFDN SysOps to
establish connections to receive RGSFDN files distributed through the
IFDC Filegate. Exceptions are made only when a policy for sharing
expenses has been agreed upon and approved by the ZC.
============================================================================
6.0 DOWNLOADABLE FILE AREA DESCRIPTIONS
The following file areas are currently being used for file transfer
in the RGSFDN system:
(*) Indicates Restricted Access
1. RGS_ADMI This area will contain RGSNet Administrative files,
such as net policy documents.
2. RGS_COOR This area will contain RGSNet specific Coordinator
Tools and Utilities.
3. RGS_DIFF This area will contain RGSNet Weekly NodeDiff Updates.
4. RGS_LIST This area will contain RGSNet Weekly NodeList Updates.
5. RGS_ALT This area will contain information on contacting and/or
joining Alternate Networks.
6. RGS_AVSC This area will contain files relating to Anti-Virus
and BBS Security.
7. RGS_BBS This area will contain utilities, text files, and
miscellanous other files relating to BBS software in
general.
8. RGS_COMM This area will contain communications programs and
related files.
9. RGS_DOOR This area will contain files and programs related to
online games, and BBS Doors in general.
10. RGS_ECHO This area will consist of files containing recent
messages found in RGSNet Message Echos and associated
RGSNet Packet Information.
11. RGS_GRFX This area will contain graphics files related to BBS
Screens and Menus.
* 12. RGS_HQ This area will contain files and distributions that
are destined for RGSNet-HQ * ONLY *.
13. RGS_MAIL This area will contain files and programs relating
to Mail and/or Nodelist Processors.
14. RGS_MISC This area will contain any file not listed or covered
elsewhere in this list.
15. RGS_OPS This area will contain files, programs, and utilities
relating to Networking and Multi-Tasking, excepting
OS/2 related.
16. RGS_OS2 This area will contain files relating to IBM OS/2
2.x and WARP programs.
17. RGS_RGDR This area will contain door programs that have been
specifically written and/or directed towards Renegade
Bulletin Board software.
18. RGS_RGNW This area will contain new Renegade BBS releases.
19. RGS_RGUT This area will contain utilities and third party
add-ons that have been specifically written and/or
directed towards Renegade Bulletin Board software.
20. RGS_TEXT This area will contain text and informational files
of both a specific and a general nature.
21. RGS_UTIL This area will contain archiving programs and their
related utilities.
============================================================================
8.0 ADDENDUM INFORMATION
- 30 DAY RULE EXCEPTION - policy is for all RGSFDN sites to hold new
distribution files unchanged for 30 days.
- NECESSARY ACTIONS TO STOP ABUSE - In the event of a site abusing policy
or other actions deemed a nuisance to other members of the network,
a warning shall be issued. If the abuse continues, file distribution to
the offender shall be requested cut, and the site removed from the
RGSFDN distribution system.
/END